DUPLICATION OF PDCP PDUS TO A RADIO CARRIER

专利摘要:
to duplicate pdcp pdus to a radio carrier, methods, devices and systems are revealed. an apparatus 300 includes a processor 305 and a transceiver 325 for communicating with a mobile communication network. processor 305 establishes 705 a radio carrier to communicate with the network, the radio carrier includes a pdcp entity, first and second rlc entities associated with said pdcp entity, first and second logical channels associated with said first and second entities rlc, respectively. the processor 305 receives a control signal from the network in 710, duplicates 715 pdus of pdcp data in the pdcp entity, and submits 720 of them to the first and second rlc entities for transmission. processor 305 indicates 725 for one of the first and second rlc entities to discard duplicate pdcp data pdus in response to the successful delivery of corresponding pdcp data pdus by the other rlc entity.
公开号:BR112019022214A2
申请号:R112019022214-6
申请日:2018-04-24
公开日:2020-05-12
发明作者:Loehr Joachim；Basu Mallick Prateek；Kuchibhotla Ravi
申请人:Motorola Mobility Llc；
IPC主号:

专利说明:

DUPLICATION OF PDCP PDUS TO A RADIO CARRIER
CROSS REFERENCE FOR RELATED ORDERS
[001] This application claims priority for the United States provisional patent application 62 / 489,332 entitled Efficient scheme for Packet Duplication in NR and filed on April 24, 2017 by Joachim Loehr, Prateek Basu Mallick and Ravi Kuchibhotla, which is incorporated into this document by reference.
FIELD
[002] The matter in question disclosed in this document concerns electronic communications and more particularly it concerns the duplication of PDCP PDUs for a radio carrier.
BACKGROUND
[003] The abbreviations and acronyms indicated below are defined in this way, at least some of which are referred to in the description below.
[004] Third Generation Partnership Project (3GPP), Mobility and Access Management Function (AMF), Access Point Name (APN), Access Stratum (AS), Carrier Aggregation (CA), Channel Evaluation Free (CCA), Control Channel Element (CCE), Channel State Information (CSI), Common Search Space (CSS), Data Network Name (DNN), Data Radio Carrier (DRB), Information Link Control (DCI), Down Link (DL),
Enhanced Free Channels (eCCA), Enhanced Broadband (eMBB), Evolved B-Node (eNB), Evolved Packet Core (EPC), Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), European Institute for Standardization of
Petition 870190107476, dated 10/23/2019, p. 18/89
2/57
Telecommunications (ETSI), Frame-Based Equipment (FBE), Frequency Division Duplexing (FDD), Frequency Division Multiple Access (FDMA), Globally Unique Temporary EU Identity (GUTI), Hybrid Automatic Repeat Request (HARQ) , Domestic Subscriber Server (HSS), Internet of
Things (loT), Key Performance Indicators (KPI), Licensed Assisted Access (LAA), Charge Based Equipment (LBE), Listening Before You Speak (LBT), Long Term Evolution (LTE), Advanced LTE (LTE-A ), Media Access Control (MAC), Multiple Access (MA), Modulation Coding Scheme (MCS), Machine Type Communication (MTC), Massive MTC (mMTC), Mobility Management (MM), Management Entity Mobility (MME), Multiple Inputs Multiple Outputs (MIMO), Multiple Path TCP (MPTCP), Shared Multiple User Access (MUSA), Non-Access Stratum (NAS), Narrow Band (NB), Network Function (NF) , B-node of
Next Generation (gNB) (for example, 5G), Next Generation Radio Access Network (NG-RAN), New Radio (NR), Policy and Charging Control (PCC), Policy Control Function (PCF), Policy Control and Billing Rules Function (PCRF), Data Network of
Packets (PDN), Packet Data Unit (PDU), PDN Communication Port (PGW), Quality of Service (QoS),
Quadrature Phase Shift Switching (QPSK), Radio Access Network (RAN), Radio Access Technology (RAT), Radio Resource Control (RRC), Receive (RX), Switch / Split Function (SSF ), Scheduling Request (SR),
Petition 870190107476, dated 10/23/2019, p. 19/89
3/57
Server Communication (SGW), Session Management Function (SMF), System Information Block (SIB), Transport Block (TB), Transport Block Size (TBS), Time Division Duplexing (TDD), Time Division Multiplexing (TDM), Transmission and Reception Point (TRP), Transmission (TX), Uplink Control Information (UCI), Unified Data Management (UDM), Entity / User Equipment (Mobile Terminal ) (UE), Uplink Link (UL), User Plan (UP), Universal Mobile Telecommunications System (UMTS), High Reliability and Low Latency Communications (URLLC) and Worldwide Interoperability for Microwave Access (WiMAX) .
[005] Some wireless communication systems support duplication of packets both for user plan data and for control plan data, in order to increase the reliability of transmissions, that is, by gaining diversity. Duplication is a function of the PDCP layer, for example, PDCP PDUs are duplicated. Services that benefit from duplication include URLLC or Radio Signaling Carriers (SRBs).
SUMMARY
[006] Methods for duplicating PDCP PDUs to a radio carrier are revealed. Apparatus and systems also perform the functions of the methods. One method (for example, of user equipment) to duplicate PDCP PDUs to a radio carrier includes establishing, on a remote unit, a radio carrier to communicate with a mobile communication network. Here, the
Petition 870190107476, dated 10/23/2019, p. 20/89
The radio carrier includes a PDCP protocol entity, a first RLC protocol entity and a second RLC protocol entity being associated with said PDCP protocol entity, a first logical channel being associated with said first RLC protocol entity , and a second logical channel being associated with said second RLC protocol entity. The method includes receiving, at the remote unit, a first control signal from the mobile communication network, duplicating PDCP data PDUs at the remote unit at the PDCP protocol entity in response to the first control signal, and submitting the PDUs from duplicate PDCP data to the first RLC protocol entity and the second RLC protocol entity for transmission. The method includes indicating to one of the first RLC protocol entity and the second RLC protocol entity to discard one or more duplicate PDCP data PDUs in response to receiving confirmation of successful transmission of one or more PDCP data PDUs corresponding by the other RLC protocol entity.
BRIEF DESCRIPTION OF THE DRAWINGS
[007] A more particular description of the modalities described above in a brief way will be presented by reference to the specific modalities that are illustrated in the attached drawings. Understanding that these drawings represent only some modalities and that, therefore, they should not be considered as limiting in scope, the modalities will be described and explained with specificity and additional details through the use of the attached drawings, in which:
figure 1 is a schematic block diagram
Petition 870190107476, dated 10/23/2019, p. 21/89
5/57 illustrating a modality of a wireless communication system for duplicating PDCP PDUs to a radio carrier;
Figure 2 is a schematic block diagram illustrating another embodiment of a network procedure for duplicating PDCP PDUs for a radio carrier;
Figure 3 is a schematic block diagram illustrating an embodiment of a user equipment apparatus for duplicating PDCP PDUs to a radio carrier;
Figure 4 is a schematic block diagram illustrating an embodiment of a network equipment apparatus for duplicating PDCP PDUs to a radio carrier;
Figure 5 is a diagram illustrating a modality of a protocol stack for duplicating PDCP PDUs to a radio carrier in a dual connectivity environment;
Figure 6 is a diagram illustrating an embodiment of a protocol stack for duplicating PDCP PDUs for a radio carrier in a carrier aggregation environment; and Figure 7 is a flow chart illustrating an embodiment of a method for duplicating PDCP PDUs to a radio carrier.
DETAILED DESCRIPTION
[008] As will be perceived by those skilled in the art, aspects of the modalities can be incorporated as a system, apparatus, method or program product. Therefore, modalities can take the form of a fully hardware modality, a fully software modality (including firmware, resident software,
Petition 870190107476, dated 10/23/2019, p. 22/89
6/57 microcode, etc.) or a modality combining software and hardware aspects.
[009] For example, the revealed modalities can be implemented at scale as a hardware circuit comprising customized circuits or arrays of very large integration ports (VLSI), ready-to-use semiconductors such as logic chips, transistors or other distinct components. The revealed modalities can also be implemented in programmable hardware devices such as field programmable gate arrays, programmable arrangement logic, programmable logic devices or the like. As another example, the disclosed modalities may include one or more physical or logical blocks of executable code that can, for example, be organized as an object, procedure or function.
[010] In addition, modalities may take the form of a program product embedded in one or more computer-readable storage devices storing machine-readable code, computer-readable code and / or program code, hereinafter referred to as code . Storage devices can be tangible, non-transitory and / or non-transmitting. Storage devices may not incorporate signals. In a certain embodiment, storage devices only employ signals to access code.
[011] Any combination of one or more computer-readable media can be used. Computer-readable media can be computer-readable storage media. The storage media readable by
Petition 870190107476, dated 10/23/2019, p. 23/89
7/57 computer can be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system device or device, or any suitable combination of those indicated above.
[012] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), a programmable, erasable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of those indicated above. In the context of this document, a computer-readable storage medium can be any tangible medium that may contain or store a program for use by or in connection with a system, apparatus or device for executing instructions.
[013] Reference throughout this specification for a similar modality or language means that a particular structure, feature or resource described in connection with the modality is included in at least one modality. Thus, meanings of the phrase in a similar modality and language throughout this specification may, but not necessarily, all refer to the same modality, but mean one or more, but not
Petition 870190107476, dated 10/23/2019, p. 24/89
8/57 all modalities unless expressly specified otherwise. The terms including, comprising, having and variations thereof mean including, but not limited to, unless expressly specified otherwise. An enumerated listing of items does not imply that some or all items are mutually exclusive, unless expressly specified otherwise. The terms one, one, o and a also refer to one or more unless expressly specified otherwise.
[014] In addition, the structures, characteristics or resources described in the modalities can be combined in any appropriate way. In the following description, numerous specific details are provided, such as programming examples, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, chips hardware, etc., to provide a complete understanding of modalities. Those skilled in the art will recognize, however, that modalities can be practiced without one or more of the specific details, or with other methods, components, materials and so on. In other instances, well-known structures, operations or materials are not shown or described in detail to avoid obscuring aspects of a modality.
[015] Aspects of the modalities are described below with reference to schematic flow diagrams and / or schematic block diagrams of methods, apparatus, systems and program products according to modalities.
Petition 870190107476, dated 10/23/2019, p. 25/89
9/57
It will be understood that each block of the schematic flow diagrams and / or of the schematic block diagrams, and of combinations of blocks in the schematic flow diagrams and / or in the schematic block diagrams, can be implemented by means of code. This code can be provided for a processor for a general-purpose computer, special-purpose computer, or other programmable data-processing device to produce a machine, such that the instructions, which execute through the computer's processor or from another programmable data processing device, they create resources to implement the functions / procedures specified in schematic flow diagrams and / or schematic block diagrams.
[016] The code can also be stored on a storage device that can direct a computer, another programmable data processing device or other devices to function in a particular way, such that the instructions stored on the storage device produce a manufacturing article including instructions that implement the function / procedure specified in the schematic flow diagrams and / or the schematic block diagrams.
[017] The code can also be loaded onto a computer, another programmable data processing device or other devices to cause a series of operational steps to be performed on the computer, another programmable device or on the other devices to produce an implemented process computer in such a way that the code that runs on the
Petition 870190107476, dated 10/23/2019, p. 26/89
10/57 computer or other programmable device provides processes to implement the functions / procedures specified in schematic flow diagrams and / or schematic block diagrams.
[018] Schematic flow diagrams and / or schematic block diagrams in the figures illustrate the architecture, functionality and operation of possible implementations of apparatus, systems, methods and program products according to various modalities. In this regard, each block in the schematic flow diagrams and / or in the schematic block diagrams can represent a module, segment or part of code, which includes one or more executable instructions from the code to implement the logical function (s) (s) specified.
[019] It should also be noted that, in some alternative implementations, the functions noted in the block may occur outside the order noted in the figures. For example, two blocks shown in succession, in fact, can be executed substantially concurrently, or the blocks can sometimes be executed in reverse order, depending on the functionality involved. Other steps and methods can be designed that are equivalent in function, logic or effect to one or more blocks, or parts thereof, of the illustrated figures.
[020] The description of elements in each figure can refer to elements of continuation figures. Like numbers refer to like elements in all figures, including alternative modalities of like elements.
[021] Figure 1 represents a wireless communication system 100 for duplicating PDCP PDUs to a carrier
Petition 870190107476, dated 10/23/2019, p. 27/89
11/57 radio, according to disclosure modalities. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, an access network 120 containing at least two base units 110, wireless communication links 115 and a mobile primary network 140. Although a number specific to remote units 105, access networks 120, base units 110, wireless communication links 115 and mobile main networks 140 is shown in figure 1, those skilled in the art will recognize that any number of remote units 105, access networks 120, base units 110, wireless communication links 115 and mobile main networks 140 can be included in wireless communication system 100. In another embodiment, access network 120 contains one or more WLAN access points ( for example, Wi-Fi ™).
[022] In an implementation, the wireless communication system 100 is compatible with the 5G system specified in the 3GPP specifications. More generally, however, the wireless communication system 100 can implement any other open or proprietary communication network, for example, LTE or WiMAX, among other networks. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
[023] In one embodiment, remote units 105 may include computing devices, such as desktop computers, laptops, personal digital assistants (PDAs), tablets, smartphones, smart TVs (for example, televisions connected to the Internet), smart devices (e.g. devices connected to the Internet), devices
Petition 870190107476, dated 10/23/2019, p. 28/89
12/57 signal converters, game consoles, security systems (including security cameras), computers on board vehicles, network devices (for example, routers, switches, modems) or similar. In some embodiments, remote units 105 include wearable devices, such as smart watches, fitness bands, optical displays worn on heads or the like. In addition, remote units 105 can be referred to as subscriber units, mobile units, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device or by other terminology used in the art. Remote units 105 can communicate directly with one or more of the base units 110 via uplink (UL) and downlink (DL) communication signals. In addition, UL and DL communication signals can be loaded on wireless communication links 115.
[024] In some embodiments, remote units 105 can communicate with a remote host 151 via a data path 125 that passes through the main mobile network 140 and a data network 150. For example, a remote unit 105 can establish a PDU connection (or a
connection of Dice) for the net data 150 through gives network main mobile 140 and the access network 120. THE network main mobile 140 So retransmits traffic between the
remote unit 105 and remote host 151 using the PDU connection to data network 150.
[025] Base units 110 can be distributed in a geographic region. In certain modalities, a unit
Petition 870190107476, dated 10/23/2019, p. 29/89
13/57 base 110 can also be referred to as an access terminal, an access point, a base, a base station, a Node-B, an eNB, a gNB, a Node-B of residence, a relay node , a device or by any other terminology used in the art. Base units 110 are generally part of a radio access network (RAN), such as access network 120, which may include one or more controllers communicatively coupled to one or more corresponding base units 110 . These and other elements of the radio access network are not illustrated, but are well known in general to people having common knowledge in the art. Base units 110 connect to mobile main network 140 through access network 120.
[026] Base units 110 can serve multiple remote units 105 within a server area, for example, a cell or a cell sector, via a wireless communication link 115. Base units 110 can be communicate directly with one or more of the remote units 105 by means of communication signals. In general, the base units 110 transmit DL communication signals to serve the remote units 105 in the time, frequency and / or spatial domain. In addition, DL communication signals can be loaded onto wireless communication links 115. Wireless communication links 115 can be any suitable carrier in licensed or unlicensed radio spectrum. Wireless communication links 115 facilitate communication between one or more of the remote units 105 and / or one or more of the base units 110.
Petition 870190107476, dated 10/23/2019, p. 30/89
14/57
[027] In one embodiment, the mobile core network 140 is a 5G core (5GC) or an evolved packet core (EPC), which can be coupled to a data network 150, such as the Internet and private data networks , among other data networks. Each primary mobile network 140 may belong to a single public terrestrial mobile network (PLMN). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
[028] The main mobile network 140 includes several network functions (NCs). As depicted, the mobile core network 140 includes multiple control plan functions including, but not limited to, an Access and Mobility Management Function (AMF) 143, a Session Management Function (SMF) 145 and a Function Policy Control (PCF). In addition, the mobile core network 140 includes a user plan function (UPF) 141 and a Unified Data Management (UDM) 147. Although specific numbers and types of network functions are represented in figure 1, those skilled in the art will recognize that any number and type of network functions can be included in the main mobile network 140.
[029] Methods, systems and devices for efficient PDCP duplication activation / deactivation for both AC and DC based architectures are revealed in this document. To efficiently enable and / or disable packet duplication (e.g., PDCP duplication), a base unit 110 signals to remote unit 105; for example, it sends a first control signal. This signaling can be PDCP control signaling, MAC control signaling
Petition 870190107476, dated 10/23/2019, p. 31/89
15/57 or RRC signaling. For 3GPP networks, the 5G radio RAT (referred to as Novo Rádio, NR) supports duplication of packets for data in both the user plane and the control plane, for example, in order to increase the reliability of transmissions by having the gain of diversity. As mentioned above, this packet duplication is a function of the PDCP layer, in such a way that PDCP PDUs are duplicated.
[030] PDCP duplication benefits services such as URLLC, where transmission reliability and latency improvements are two key aspects. In addition, redundancy / diversity schemes in Carrier Aggregation (CA) scenarios can be used to meet the reliability and latency requirements of URLLC. For URLLC, two independent transmission channels on different carriers may be necessary for cases of extreme reliability such as error rates of 10 ⁵ to 10 ⁹ within a given latency limit. Here, CA-based duplication is a tool available to the scheduler to further improve transmission reliability. However, where reliability in one of the carriers cannot be guaranteed, it is beneficial to have additional carrier (s) available. As an example, such a situation may be due to a temporary lack / fading, due to an unanticipated change or wrong channel status information.
[031] Duplication of packets can also be applied based on Dual Connectivity (DC) architecture; for example, split carrier operation with PDCP duplication. In a general sense, packet duplication can be
Petition 870190107476, dated 10/23/2019, p. 32/89
16/57 used in conjunction with different diversity schemes involving more than one radio link to serve a UE. Although the following modalities focus on DC and CA scenarios, the present disclosure is not proposed to be limited to those implementations.
[032] In general, packet duplication is limited to those situations where extra reliability is needed such as, for example, dynamic activation / deactivation. Here, PDCP control signaling or MAC control signaling (for example, MAC control element (CE)) can be used to enable / disable PDCP duplication. This also advantageously reduces the overhead of enabling / disabling PDCP duplication. Currently, there are no procedures for configuring PDCP duplication in architecture based on either CA or DC, let alone procedures for enabling / disabling duplication in a flexible and dynamic mode.
[033] In one embodiment, remote unit 105 is configured with a split carrier, for example, for dual connectivity. In such embodiments, the default state for PDCP duplication on the split carrier can be deactivated, where the base unit 110 explicitly activates PDCP duplication when sending the first control signal. In another embodiment, remote unit 105 communicates with access network 120 using carrier aggregation, remote unit 105 being configured with at least one carrier that has a PDCP entity that is associated with two logical channel / RLC entities being mapped for different server cells. In such modalities, the default state for PDCP duplication of
Petition 870190107476, dated 10/23/2019, p. 33/89
17/57 carrier can be deactivated, where base unit 110 explicitly activates PDCP duplication when sending the first control signal.
[034] In one embodiment, when duplication is activated, remote unit 105 removes PDCP PDUs from transmission temporary storage associated with a channel / RLC logical entity that has already been successfully transmitted through another channel / logical entity RLC, for example, in order to prevent the transmission buffer from becoming full. The removal (discard) of packages can be based on received RLC status reports, according to one modality. Here, an RLC layer on remote unit 105 informs a PDCP layer about the successfully transmitted PDCP PDUs. The PDCP layer can then send a PDCP discard notification to the other RLC entity.
[035] Alternatively, packet removal / disposal may be based on received PDCP status reports. In such embodiments, remote unit 105 sends PDCP status reports to base unit 110 for DL, base unit 110 using this information to discard packets that have already been successfully received by remote unit 105 from temporary storage. DL transmission system. Similarly, for UL, the PDCP layer on remote unit 105 receives a PDCP status report from base unit 110 and indicates to the appropriate RLC entity to drop packets that have already been successfully transmitted (for example, by another RLC entity). In an implementation, remote unit 105 lets the PDCP discard timer expire for those PDCP SDUs that are
Petition 870190107476, dated 10/23/2019, p. 34/89
18/57 indicated in the PDCP status report as successfully transmitted and subsequently sends the discard notification to the RLC layer correspondingly in response to the PDCP discard timer expiration.
[036] Figure 2 represents a network procedure 200 for duplicating PDCP PDUs to a radio carrier, according to the disclosure modalities. The network procedure 200 involves a UE 205 and a network entity, represented here as gNB 210. The UE 205 can be an embodiment of the remote unit 105 described above. Likewise, gNB 210 can be an embodiment of the base unit 110 described above.
[037] Here, it is assumed that the UE 205 has established a radio carrier with gNB 210. Here, the radio carrier can include a PDCP entity, a first RLC entity and a second RLC entity associated with the PDCP entity, a first logical channel being associated with the first RLC entity, and a second logical channel associated with the second RLC protocol entity. In one embodiment, the radio carrier includes a carrier split in the UE 205 (for example, for dual connectivity with gNB 210 and with another network entity (not shown)). In another embodiment, the radio carrier can be used in a carrier aggregation implementation.
[038] Network procedure 200 begins with gNB 210 by sending to UE 205 a first control signal used to activate packet duplication (see signal 215) for said radio carrier. Here, the first control signal can be a PDCP control signal, a MAC control signal and / or an RRC signal. As noted
Petition 870190107476, dated 10/23/2019, p. 35/89
19/57 previously, packet duplication can be disabled as a standard, thus requiring an explicit signal (here, the first control signal) from gNB 210 to activate duplication for a radio carrier.
[039] In certain embodiments, the gNB 210 optionally sends to the UE 205 an indication of which RLC entity to use for transmission of PDCP PDUs by disabling packet duplication (see signaling 220). In one embodiment, the unused RLC entity is deactivated until duplication is activated again. In another mode, the unused RLC entity becomes available for data transmission (not duplicated) by disabling packet duplication.
[040] In response to the first control signal, the UE 205 starts duplicating packets by duplicating PDUs of PDCP data in the PDCP entity (see block 225). Here, copies of the same PDCP of PDCP data are sent to the first and second RLC entities. In other words, the PDCP PDUs received by the first and second RLC entities contain the same information. Therefore, RLC entities further process duplicate packets for transmission. Here, routing of PDCP data PDUs to both RLC entities can be based on UL leases received. As shown, the UE 205 transmits the duplicated PDCP data PDUs to gNB 210 via the first and second RLC entities (see message 230).
[041] In several embodiments, gNB 210 indicates successful transmission of (certain) PDUs of PDCP data to an RLC entity (see signaling 235). Here, the gNB 210 can send an RLC status report indicating the
Petition 870190107476, dated 10/23/2019, p. 36/89
20/57 successful transmission of RLC PDUs corresponding to PDCP data PDUs. Alternatively, gNB 210 can send a PDCP status report to indicate successful transmission of PDUs of PDCP data.
[042] In response to successfully transmitting PDCP data PDUs through an RLC entity, the UE 205 removes corresponding PDCP data PDUs from the other RLC entity's temporary storage (see block 240). In some embodiments, successful transmission is indicated via an RLC status report and the PDCP entity receives the successful delivery indication from the RLC entity and signals to the other RLC entity to discard the corresponding PDCP data PDUs. In other modalities, the PDCP entity receives the indication of successful delivery through a PDCP status report. Note that the UE 205 continues to send duplicate PDCP data PDUs to the gNB 210 and continues to receive successful delivery indications.
[043] At some point later in time, gNB 210 sends a second control signal to UE 205 to disable packet duplication (see signal 245). Again, PDCP control signaling, MAC control signaling and / or RRC signaling can be used to send the second control signal. In response to receiving the second control signal, the UE 205 stops duplicating PDUs of PDCP data at the radio carrier's PDCP entity (see block 250). Note that the UE 205 uses the RLC entity / logical channel previously configured for PDCP data transmission after disabling packet duplication.
[044] In certain modalities, the UE 205 cancels an
Petition 870190107476, dated 10/23/2019, p. 37/89
21/57 scheduling request activated by data arrival from RLC entity / logical channel which is configured not to be used for PDCP data transmission when duplication is disabled, responsive to the second control signal. In certain embodiments, the UE 205 cancels a temporary storage status report (BSR) activated by data arrival from the logical channel that is configured not to be used for PDCP data transmission when duplication is disabled, responsive to the second control signal. In addition, a MAC / HARQ entity on UE 205 can drop packets associated with the disabled RLC entity. In certain embodiments, the UE 205 empties the RLC transmission buffer from the disabled RLC entity as a response to receiving the second control signal.
[045] Figure 3 represents a modality of a user equipment apparatus 300 that can be used to duplicate PDCP PDUs to a radio carrier, according to the disclosure modalities. User equipment apparatus 300 may be a form of remote unit 105 and / or UE 205. In addition, user equipment apparatus 300 may include a processor 305, a memory 310, an input device 315, a device output 320 and a transceiver 325. In some embodiments, the input device 315 and the output device 320 are combined into a single device, such as a touch screen. In certain embodiments, the user equipment apparatus 300 does not include any input device 315 and / or output device 320.
[046] As shown, transceiver 325 includes at least one transmitter 330 and at least one receiver 335.
Petition 870190107476, dated 10/23/2019, p. 38/89
22/57
In addition, transceiver 325 can support at least one network interface 340. Here, at least one network interface 340 facilitates communication with an eNB or gNB (for example, using the Uu interface). In addition, the at least one network interface 340 may include an interface used for communications with a UPF and / or AMF.
[047] Processor 305, in one embodiment, can include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, processor 305 can be a microcontroller, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processing unit, an array of field programmable ports (FPGA) or controller similar programmable. In some embodiments, processor 305 executes instructions stored in memory 310 to execute the routines and methods described in this document. Processor 305 is communicatively coupled to memory 310, input device 315, output device 320 and transceiver 325.
[048] In some embodiments, the 305 processor establishes a radio carrier to communicate with a mobile communication network. Here, the radio bearer includes a PDCP protocol entity, a first RLC protocol entity and a second RLC protocol entity being associated with said PDCP protocol entity, a first logical channel being associated with said first RLC protocol entity , and a second logical channel being associated with said second entity
Petition 870190107476, dated 10/23/2019, p. 39/89
23/57 of RLC protocol. In various embodiments, the radio carrier may include a MAC entity associated with the first RLC protocol entity and a MAC entity associated with the second RLC protocol entity.
[049] In response to receiving a first control signal, processor 305 starts duplicating packets. Here, processor 305 duplicates PDCP data PDUs in the PDCP protocol entity in response to the first control signal. Duplicate PDCP data PDUs are submitted to the first RLC protocol entity and the second RLC protocol entity for transmission. In addition, processor 305 instructs the first RLC protocol entity to discard one or more duplicate PDCP data PDUs in response to receiving confirmation of successful transmission of one or more corresponding PDCP data PDUs by the second protocol entity RLC and also instructs the second protocol entity to discard one or more duplicate PDCP data PDUs in response to receiving confirmation of successful transmission of one or more corresponding PDCP data PDUs by the first RLC protocol entity.
[050] In some embodiments, an RLC protocol entity indicates successful delivery of one or more PDUs of corresponding PDCP data to the PDCP protocol entity based on an RLC status report received from the mobile communication network. In response to receiving said indication of successful delivery, the PDCP protocol entity indicates, for the other of the first and second RLC protocol entities, to discard one or more PDUs of duplicate PDCP data. In certain
Petition 870190107476, dated 10/23/2019, p. 40/89
24/57 modalities, processor 305 discards one or more PDCPs of PDCP data at the appropriate RLC entity in response to receiving the discard indication from the PDCP protocol entity. In some embodiments, processor 305 discards one or more PDUs of PDCP data in one of the first RLC protocol entity and the second protocol entity
RLC with on the basis of a PDCP status Received gives network mobile communication. [051] In various modalities, the 305 processor, in answer at the first sign of control, indicates an
number of data packets (for example, PDCP data PDUs) in the PDCP protocol entity for the MAC entity associated with the first RLC protocol entity and for the MAC entity associated with the second RLC protocol entity to report the status of temporary storage of the logical channels associated with the first RLC protocol entity and the second RLC protocol entity. Here, the same quantities of data packets are indicated for both RLC entities.
[052] In some embodiments, the first control signal instructs the user equipment device 300 to begin duplicating PDUs of PDCP data. In several modalities, the first control signal is one of: a PDCP control signal, a MAC control signal and an RRC signal. At some time after receiving the first control signal, processor 305 may additionally receive a second control signal that instructs user equipment apparatus 300 to stop duplicating PDCP data PDUs. Here it is assumed that the user equipment device 300 is to use the first RLC protocol entity to
Petition 870190107476, dated 10/23/2019, p. 41/89
25/57 PDUs transmission of PDCP data when disabling packet duplication.
[053] In one embodiment, processor 305 can cancel an escalation request associated with the second logic channel in response to the second control signal. Here, the scheduling request is activated by data arrival for the second logical channel. In another embodiment, processor 305 can cancel a buffering status report associated with the second logical channel in response to the second control signal. Here, the staging status report is activated by data arrival for the second logical channel.
[054] In certain embodiments, the user equipment device 300 communicates with the mobile communication network using dual connectivity. In the case of using dual connectivity, each of the RLC protocol entities belongs to a different group of cells in the mobile communication network. In addition, the MAC entity associated with the first RLC protocol entity is a first MAC entity and the MAC entity associated with the second RLC protocol entity is a second MAC entity different from that first. In such embodiments, processor 305 indicates an equal amount of PDCP data PDUs in the PDCP protocol entity for the first MAC entity and for the second MAC entity to report the buffer status of the first logical channel and the second logical channel.
[055] Also for the dual connectivity use case, establishing the radio carrier may include establishing
Petition 870190107476, dated 10/23/2019, p. 42/89
26/57 a carrier divided into the user equipment apparatus. Here, the split carrier supports dual connectivity. In certain embodiments, the first control signal comprises an indication to duplicate PDUs of PDCP data on the split carrier. In certain embodiments, the processor establishes an uphill link data split threshold for a value of zero in response to receiving the first control signal and establishes the uphill link data split threshold in response to receiving a second control signal, where the first control signal enables packet duplication and the second control signal disables packet duplication.
[056] In certain embodiments, the user equipment device 300 communicates with the mobile communication network using carrier aggregation. In the case of using carrier aggregation, the first RLC protocol entity and the second RLC protocol entity belong to the same group of cells. In addition, each of the RLC protocol entities is associated with the same (for example, shared) MAC entity. In such embodiments, processor 305 indicates the same amount of PDCP data PDUs in the PDCP protocol entity to the MAC entity to report the buffer status of the first logical channel and the second logical channel.
[057] In additional modes, processor 305 receives a second control signal and disables packet duplication. Here, in response to the second control signal, processor 305 can indicate a number of PDCP data PDUs available for transmission in the PDCP protocol entity to the MAC entity associated with the second
Petition 870190107476, dated 10/23/2019, p. 43/89
27/57 RLC protocol entity to report temporary storage status of the second logical channel to zero. Note here that the first RLC protocol entity continues to send packets (for example, PDCP data PDUs) after disabling packet duplication. In addition, processor 305 can receive a third control signal before the second control signal, the third control signal indicating to use the first RLC protocol entity to transmit PDUs of PDCP data when disabling packet duplication.
[058] In some embodiments, processor 305 initializes a symbol bucket status to a previously inactive logical channel (for example, in response to the first control signal). Here, the number of symbols in the symbol bucket can be increased periodically. In addition, the previously inactive logical channel can be one of the first logical channel and the second logical channel. In response to receiving the second control signal disabling packet duplication, processor 305 does not maintain a bucket of symbols associated with the second logical channel.
[059] Memory 310, in one embodiment, is a computer-readable storage medium. In some embodiments, memory 310 includes volatile computer storage media. For example, memory 310 may include RAM, including dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM) and / or static RAM (SRAM). In some embodiments, memory 310 includes non-volatile computer storage media. For example, memory 310 may include a hard drive, flash memory or any other computer storage device
Petition 870190107476, dated 10/23/2019, p. 44/89
28/57 suitable non-volatile. In some embodiments, memory 310 includes both volatile and non-volatile computer storage media. In some embodiments, memory 310 stores data relating to duplicating PDCP PDUs for a radio carrier; for example, stores indications to enable / disable packet duplication, indications of successful transmission of PDCP data PDUs, and more. In certain embodiments, memory 310 also stores program code and related data, such as an operating system or other controller algorithms operating on user equipment apparatus 300 and one or more software applications.
[060] Input device 315, in one embodiment, can include any known computer input device, including a touch panel, button, keyboard, pointer, microphone, or the like. In some embodiments, the input device 315 can be integrated with the output device 320, for example, as a touchscreen or similar touchscreen. In some embodiments, the input device 315 includes a touch screen in such a way that text can be entered using a virtual keyboard displayed on the touch screen and / or when typing on the touch screen. In some embodiments, the input device 315 includes two or more different devices, such as a keyboard and a touch panel.
[061] Output device 320, in one embodiment, can include any known electronically controllable display or display device. The output device 320 can be designed to produce visual signals,
Petition 870190107476, dated 10/23/2019, p. 45/89
29/57 audible and / or tactile. In some embodiments, the output device 320 includes an electronic display capable of producing visual data for a user. For example, output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector or similar display device capable of producing images, text or the like for a user. As another non-limiting example, output device 320 may include a wearable display such as a smart watch, smart glasses, an alert display or the like. Additionally, the output device 320 can be a component of a smartphone, a personal digital assistant, a television, a desktop computer, a notebook (laptop), a personal computer, a vehicle panel or the like.
[062] In certain embodiments, the output device 320 includes one or more speakers to produce sound. For example, output device 320 can produce an audible alert or notification (for example, a beep or bell). In some embodiments, the output device 320 includes one or more tactile devices to produce vibrations, movement or other tactile feedback. In some embodiments, all or some parts of the output device 320 can be integrated with the input device 315. For example, the input device 315 and the output device 320 can form a touchscreen or similar touchscreen. In other embodiments, all or some parts of the output device 320 may be located close to the
Petition 870190107476, dated 10/23/2019, p. 46/89
30/57 entry 315.
[063] Transceiver 325 communicates with one or more network functions of a mobile communication network. Transceiver 325 operates under the control of processor 305 to transmit messages, data and other signals and also to receive messages, data and other signals. For example, processor 305 can selectively activate the transceiver (or parts thereof) at particular times in order to send and receive messages. Transceiver 325 may include one or more transmitters 330 and one or more receivers 335.
[064] Figure 4 represents a modality of a network equipment device 400 that can be used to duplicate PDCP PDUs to a radio carrier, according to the disclosure modalities. The network equipment apparatus 400 may be a form of the base unit 110 and / or gNB 210. In addition, the network equipment apparatus 400 may include a processor 405, a memory 410, an input device 415, a output device 420 and a transceiver 425. In some embodiments, input device 415 and output device 420 are combined into a single device, such as a touchscreen. In certain embodiments, the network equipment apparatus 400 does not include any input device 415 and / or output device 420.
[065] As shown, transceiver 425 includes at least one transmitter 430 and at least one receiver 435. Additionally, transceiver 425 can support at least one 440 network interface. Here, at least one 440 network interface facilitates communication with a remote unit 105, such as the UE 205, with other network functions in a
Petition 870190107476, dated 10/23/2019, p. 47/89
31/57 main mobile network 140, such as UPF 141, AMF 143 and others.
[066] The 405 processor, in one embodiment, can include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, processor 405 can be a microcontroller, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processing unit, an array of field programmable ports (FPGA) or controller similar programmable. In some embodiments, processor 405 executes instructions stored in memory 410 to execute the routines and methods described in this document. Processor 405 is communicatively coupled to memory 410, input device 415, output device 420 and transceiver 425.
[067] In several embodiments, processor 405 establishes a radio bearer to communicate with a UE, such as the UE 205. Here, the radio bearer can include a PDCP protocol entity, a first RLC protocol entity and a second RLC protocol entity being associated with said PDCP protocol entity, a first logical channel being associated with said first RLC protocol entity, and a second logical channel being associated with said second RLC protocol entity.
[068] In some embodiments, the 405 processor transmits a first control signal to a UE, the first control signal instructing the UE to begin
Petition 870190107476, dated 10/23/2019, p. 48/89
32/57 duplication of packages. In certain modalities, the first
signal control is one of: one signal in PDCP control, one signal in MAC control and one signal RRC In response The to transmit the first sign in control, the processor 405
receives duplicate packet (for example, duplicate PDCP data PDUs from the UE). In addition, processor 405 indicates to the UE successful transmission of one or more PDUs of UL PDCP data.
[069] In certain embodiments, processor 405 additionally receives from the UE an indication of DL PDCP data PDUs received successfully. Where duplication of
packages is used in DL, the processor 405 can discard gives first entity RLC protocol an or more PDUs in data from PDCP in first entity in protocol RLC in
response to the successful transmission of one or more corresponding entities of the second RLC protocol and vice versa.
[070] At a time after sending the first control signal, processor 405 can additionally send a second control signal that instructs the UE to stop duplicating PDUs of PDCP data. In several embodiments, processor 405 sends the UE an indication of which RLC protocol entity to use for transmitting PDUs of PDCP data when disabling packet duplication.
[071] Memory 410, in one mode, is a computer-readable storage medium. In some embodiments, memory 410 includes volatile computer storage media. For example, memory 410 may include RAM, including dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM) and / or static RAM (SRAM). In some
Petition 870190107476, dated 10/23/2019, p. 49/89
33/57 modes, the 410 memory includes non-volatile computer storage media. For example, memory 410 may include a hard disk drive, flash memory or any other suitable non-volatile computer storage device. In some embodiments, memory 410 includes both volatile and non-volatile computer storage media. In some embodiments, memory 410 stores data relating to duplicating PDCP PDUs to a radio carrier; for example, stores indications to enable / disable packet duplication, indications of successful transmission of PDCP data PDUs, and more. In certain embodiments, memory 410 also stores program code and related data, such as an operating system or other controller algorithms operating on the network equipment 400 and one or more software applications.
[072] Input device 415, in one embodiment, can include any known computer input device including a touch panel, button, keyboard, pointer, microphone, or the like. In some embodiments, the input device 415 can be integrated with the output device 420, for example, as a touchscreen or similar touchscreen. In some embodiments, the input device 415 includes a touch screen in such a way that text can be entered using a virtual keyboard displayed on the touch screen and / or by hand writing on the touch screen. In some embodiments, the input device 415 includes two or more different devices, such as a keyboard and a touch panel.
Petition 870190107476, dated 10/23/2019, p. 50/89
34/57
[073] Output device 420, in one embodiment, can include any known electronically controllable display or display device. Output device 420 can be designed to produce visual, audible and / or tactile signals. In some embodiments, the output device 420 includes an electronic display capable of producing visual data for a user. For example, the output device 420 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector or similar display device capable of producing images, text or the like for a user. As another non-limiting example, output device 420 may include a wearable display such as a smart watch, smart glasses, an alert display or the like. Additionally, the output device 420 can be a component of a smartphone, a personal digital assistant, a television, a desktop computer, a notebook (laptop), a personal computer, a vehicle panel or the like.
[074] In certain embodiments, the output device 420 includes one or more speakers to produce sound. For example, output device 420 may produce an audible alert or notification (for example, a beep or bell). In some embodiments, the output device 420 includes one or more tactile devices to produce vibration, movement or other tactile feedback. In some embodiments, all or parts of the output device 420 can be integrated with the input device 415. For example, the input device 415 and the input device
Petition 870190107476, dated 10/23/2019, p. 51/89
35/57 output 420 can form a touchscreen or similar touchscreen. In other embodiments, all or parts of the output device 420 can be located close to the input device 415.
[075] Transceiver 425 operates under the control of processor 405 to transmit messages, data and other signals, and also to receive messages, data and other signals. For example, the 405 processor can selectively activate the transceiver (or parts of it) at particular times in order to send and receive messages. Transceiver 425 may include one or more transmitters 430 and one or more receivers 435.
[076] Figure 5 represents a protocol stack 500 for duplicating PDCP PDUs to a radio carrier in a dual connectivity environment, according to the disclosure modalities. Here, the protocol stack 500 is represented as a part of UE 205. As shown, the protocol stack 500 includes a first PDCP 505 entity and a second PDCP 510 entity. Here, there is one PDCP entity per radio carrier, such that the first PDCP 505 entity belongs to a first radio carrier and the second PDCP 510 entity belongs to a second radio carrier. PDCP 505-510 entities are located on a PDCP layer of protocol stack 500 and perform PDCP functions, including (but not limited to) header compression, security (integrity and encryption protection) and support for reordering and retransmission, for example example, during transfer. Note that the PDCP layer processes RRC messages in the control plane and IP packets in the user plane.
Petition 870190107476, dated 10/23/2019, p. 52/89
36/57
[077] Protocol stack 500 also includes a first RLC 515 entity, a second RLC 520 entity and a third RLC 525 entity. There may be multiple RLC entities per radio carrier. In the represented modality, the first RLC 515 entity and the second RLC 520 entity belong to the same radio carrier as the first PDCP 505 entity. Note that the third RLC 525 entity is associated with the second PDCP 510 entity. The RLC 515-525 entities are located on an RLC layer of the protocol stack 500 and perform RLC functions, including (but not limited to) segmenting and reassembling packets to adapt them to the appropriate radio interface size. Note that the RLC layer exists below the PDCP layer and above the MAC layer. Protocol stack 500 includes three different logical channels: a first logical channel 530 on a MAC entity 540 associated with the master cell group (MAC MACG) associated with the third RLC entity 525 and a second logical channel 535 associated with the second RLC entity 520. Protocol stack 500 also includes a first logical channel 550 in a MAC entity 545 associated with a secondary group of cells (the MAC SCG) associated with the first RLC entity 515.
[078] In the represented mode, the UE 205 is configured with a divided carrier, thus having a MAC 540 entity associated with a group of master cells and
an entity MAC 545 associated with a group of cells secondary. On here, The first entity RLC 515 is associated with MAC SCG 545, While what the second RLC entity 520 and the third entity RLC 525 are
Petition 870190107476, dated 10/23/2019, p. 53/89
37/57 associated with MAC MCG 540. MAC entities 540-545 are located on a MAC layer of the protocol stack 500 and perform MAC functions, including (but not limited to) multiplexing between logical channels and transport channels (PHY) . MAC 540-545 entities build transport blocks (TBs) from SDUs received from the RLC layer. As used in this document, a service data unit (SDU) refers to data received from a higher layer and a protocol data unit (PDU) refers to data passed to a lower layer. Thus, PDCP 505-510 entities produce PDCP PDUs, which are referred to as RLC SDUs when received at RLC 515-525 entities. Likewise, RLC 515-525 entities produce RLC PDUs, which are referred to as MAC SDUs when received at the corresponding MAC entities.
[079] In several modalities, PDCP duplication is used in a DC-based architecture, such as that scenario supported by the protocol stack 500. Here, a network entity (NE) such as a base unit or gNB configures a split carrier for UE 205. On the network side, the PDCP layer of the split carrier can be located on the Master Node (MN) or on the Secondary Node (SN). In addition, the UE 205 can be additionally configured with a Master Cell Group (MCG) carrier (s) or with a Secondary Cell Group (SCG) carrier (s). Here, MCG carriers are multiplexed (and demultiplexed) by MAC MCG 540, while SCG carriers are multiplexed (and demultiplexed) by MAC SCG 545.
[080] The NE, for example, an MN or an SN, signals to
Petition 870190107476, dated 10/23/2019, p. 54/89
38/57 the UE 205 the PDCP duplication configuration, for example, duplication activation / deactivation. Note that the default state for duplication is disabled. Therefore, the NE, for example, the MN or SN, needs to explicitly activate PDCP duplication when a split carrier used for duplication is configured. As previously discussed, this signaling can be PDCP control signaling or MAC control signaling. Alternatively, RRC signaling can be used.
[081] According to one modality, the NE configures the UE 205 with a radio link, for example, the MCG or SCG, which the UE 205 must use for data transmission when PDCP duplication is disabled. In certain modalities, this configuration can be done by means of RRC signaling. For example, the Information Element (IE) ulDataSplitDRB-ViaSCG can be used to define whether the UE 205 sends UL data through the SCG or MCG of a configured split carrier.
[082] For the case where the NE activates PDCP duplication, the UE 205 reports the same PDCP temporary storage occupation of the split carrier used for duplication within the temporary storage status report (BSR) for both MAC 540-545 entities respectively for both MN and SN. Here, routing of PDCP data PDUs to the first and second RLC 515-520 entities can be based on UL leases received. For example, when a UL grant is received for a CG, the corresponding PDCP PDUs are generated, duplicated and (optionally) forwarded to the first and second RLC 515520 entities.
Petition 870190107476, dated 10/23/2019, p. 55/89
39/57
[083] Note that UE 205 and / or NE can control duplication of PDCP from PDCP using a threshold associated with the split carrier, such as the ulDataSplitThreshold threshold. Here, when the data available for transmission in PDCP is equal to or greater than ulDataSplítThreshold, then the UE 205 reports to both (all) network entities the same amount of PDCP data for the purpose of reporting staging status.
[084] In some modalities, the UE 205 sets ulDataSplítThreshold to zero in response to receiving the first NE control signal, for example, MN or SN, enabling duplication. Setting ul-DataSplitThreshold to zero ensures that the data on the first PDCP 505 entity is reported for both network nodes, that is, for both MN and SN. Here, UE 205 indicates the data available for transmission in PDCP for both the MAC 545 entity configured for SCG and the MAC 540 entity configured for MCG. In other modalities, the NE, for example, the MN or the SN, sets the ul-DataSplitThreshold to zero when activating PDCP duplication. The configuration can be signaled by means of PDCP control signaling or MAC control signaling or alternatively by RRC signaling.
[085] Transmission of the PDCP PDUs takes place according to the received uplink link concessions. For example, the UE 205 submits the generated PDCP PDUs to the first RLC 515 entity configured for SCG or to the second RLC 520 entity configured for MCG, whichever has requested the PDUs. Additionally, the UE 205 can
Petition 870190107476, dated 10/23/2019, p. 56/89
40/57 duplicate the generated PDCP PDUs and you can submit them to the other RLC entity.
[086] In some embodiments, the UE 205 sets ulDataSplitThreshold to infinity in response to receiving a second control signal from the NE directing the UE 205 to disable duplication. Here, setting ulDataSplitThreshold to infinity ensures that only one radio link, for example, as configured by ulDataSplitDRB-ViaSCG, is used for data transmissions. In certain embodiments the UE 205 empties the RLC transmission buffer of the inactive RLC entity, i.e., the inactive radio link RLC entity. Here, emptying the PDCP PDUs / RLC PDUs stored in the transmission temporary storage ensures that those PDUs are not retransmitted once the radio link is reactivated (when duplication is activated again), as this can result in TCP reducing the HFN link rate and / or desynchronization. In other modalities, the RLC entity of the inactivated radio link is reestablished when duplication is deactivated.
[087] In some modalities, logical channels 530, 535 and 550 can be associated with symbol buckets, used to control uphill link transmissions. Here, MAC 540-545 entities maintain a variable Bj for each logical channel j, Bj representing the status of the symbol bucket for that logical channel, for example, the number of symbols accumulated for that logical channel. In various modalities, the bucket status of symbols Bj is initialized to zero when the related logical channel is established, and incremented by the product PBR x duration of
Petition 870190107476, dated 10/23/2019, p. 57/89
41/57
TTI for each TTI, where PBR is Prioritized Bit Rate of logical channel j. In certain embodiments, the UE 205 initializes Bj for a logic channel j inactive previously to zero when duplication is activated (for example, it sets the number of symbols in the bucket of logic channel j to zero). In certain embodiments, the value of Bj can be initialized to zero for an inactive logical channel when duplication is disabled. In various embodiments, the UE 205 does not maintain the symbol bucket status of an inactive logical channel when duplication is disabled; for example, the UE 205 stops increasing the bucket status of symbols Bj.
[088] In certain modalities, the UE 205 cancels, if any, Scheduling Requests enabled and / or temporary storage status reports caused by data arrival from the inactivated logical channel when duplication is deactivated. Note that the Escalation Request (s) and / or temporary storage status report (s) are activated by data arrival for the now inactive logical channel.
[08 9] In one mode the link group / radio cell inactive RLC entity, for example, split carrier leg, is suspended when duplication is disabled. Here, the corresponding MAC entity does not report temporary storage status information for the split carrier's suspended leg. In certain embodiments, the UE 205 empties the RLC temporary storage or alternatively restores the suspended RLC entity. In one mode the MAC entity (or HARQ entity) discards packets that are received for an RLC entity from an inactive leg of a split carrier when
Petition 870190107476, dated 10/23/2019, p. 58/89
42/57 duplication is disabled. RLC PDUs of an inactive RLC entity / logic channel entity may still be subject to HARQ retransmission and therefore arrive after duplication has been disabled.
[090] Figure 6 represents a protocol stack 600 for duplicating PDCP PDUs to a radio carrier in a carrier aggregation environment, according to the disclosure modalities. Here, the protocol stack 600 is represented as a part of UE 205. As shown, the protocol stack 600 includes a first PDCP 505 entity and a second PDCP 510 entity. Here, there is one PDCP entity per radio bearer. PDCP 505-510 entities are located on a PDCP layer of protocol stack 600 and perform PDCP functions.
[091] Protocol stack 600 also includes a first RLC 515 entity, a second RLC 520 entity and a third RLC 525 entity. In the embodiment shown, the first RLC 515 entity and the second RLC 520 entity belong to the same radio carrier as the first PDCP 505 entity. Note that the third RLC 525 entity is associated with the second PDCP 510 entity belonging to a second radio carrier. The RLC 515-525 entities are located on an RLC layer of the protocol stack 500 and perform RLC functions, including (but not limited to) segmenting and reassembling packets to adapt them to the appropriate size for the radio interface. Protocol stack 600 includes a first logical channel 610 associated with the first RLC entity 515, a second logical channel 615 associated with the second RLC entity 520 and a third logical channel 620 associated with the third entity
Petition 870190107476, dated 10/23/2019, p. 59/89
43/57
RLC 525.
[092] In the represented mode, UE 205 is configured for carrier aggregation, thus having a single MAC 605 entity associated with logical channels 610615. MAC 605 entity is located on a MAC layer of the protocol stack 600 and performs MAC functions .
[093] In several modalities, PDCP duplication is used in a CA-based architecture, such as that supported by the 600 protocol stack. An NE, for example, a gNB, configures the UE 205 with a first PDCP 505 entity that is mapped for the two RLC 515-520 entities. Here, PDCP PDUs can be mapped to two different logical channels (for example, logical channels 610-615). In one embodiment, the two logical channels are mapped to different groups of logical channels for the purpose of reporting temporary storage status; for example, a separate staging status being reported for the two logical channels 610-615. The MAC 605 entity ensures that duplicate PDCP PDUs are mapped to different carriers or optionally to different Transport Blocks (TBs) during the LCP procedure.
[094] The NE, for example, gNB, signals the UE 205 the PDCP duplication configuration, for example, enabling / disabling packet duplication. In certain embodiments, this signaling can be PDCP control signaling or MAC control signaling. Alternatively, the signaling can be RRC signaling. According to one embodiment, the NE configures the UE 205 with an RLC entity, which the UE 205 uses for PDCP data transmission when packet duplication is disabled. In
Petition 870190107476, dated 10/23/2019, p. 60/89
44/57 certain modalities, this configuration can be done through RRC signaling.
[095] In one mode, when duplication is activated, the UE 205 reports the same PDCP temporary storage occupation within the temporary storage status report (BSR) for both logical channels 610-615 associated with the first PDCP 505 entity. Routing in
PDCP PDUs for both entities RLC is based in concessions UL received, that is, When the UE 205 receives an concession UL and the MAC entity 605 indicates (such as one result in LCP procedure) for one in the two channels
RLC entities / logics the amount of data for transmission, the corresponding PDCP PDUs are generated, duplicated and can be forwarded to the indicated RLC entity and can also be to the other RLC entity / logic channel.
[096] According to some modalities, the NE signals the UE a configuration directing the UE 205 to use only one RLC entity / logic channel or both of the RLC entity / logic channels, for example, disabling / enabling duplication. As noted earlier, this configuration can be signaled by means of PDCP control signaling, MAC control signaling or RRC signaling. In certain embodiments, the default state for duplication is deactivated when the PDCP entity is configured with two logical channel / RLC entities. Thus, the NE may need to explicitly enable PDCP duplication.
[097] In certain embodiments, in response to receiving an NE indication directing the UE 205 to disable duplication, the UE 205 empties the temporary storage of
Petition 870190107476, dated 10/23/2019, p. 61/89
45/57 RLC transmission of the RLC entity disabled (for example, the RLC entity / logic channel that is not used for data transmission as indicated by configuration). In certain modalities, the data available for transmission in PDCP for the disabled channel / RLC entity is set to zero. Alternatively, the MAC 605 entity may not report temporary storage status information for the disabled RLC entity / logic channel. According to another embodiment, the UE 205 can reestablish the RLC entity that is not used for data transmission.
[098] In certain modalities, The HUH 205 suspend the entity channel / logic RLC that does not is used for streaming of data when NE directs the HUH 205 to disable
duplication. Here, the MAC 605 entity does not report temporary storage status information for the suspended logical channel. Alternatively, the UE 205 can reinstate the RLC entity from the suspended logical channel or empty the RLC buffer as discussed above.
[099] In some embodiments, logic channels 610-620 can be associated with buckets of symbols, used to control transmissions. Here, the MAC 605 entity can maintain a variable Bj for each logical channel j, Bj representing the status of the symbol bucket for that logical channel. In various modalities, the bucket status of symbols Bj is initialized to zero when the related logical channel is established, and incremented by the product PBR x TTI duration for each TTI, where PBR is Prioritized Bit Rate of logic channel j. In certain embodiments, the UE 205 initializes Bj to an inactive logical channel (or
Petition 870190107476, dated 10/23/2019, p. 62/89
46/57 suspended) previously to zero when duplication is activated (for example, it sets the number of symbols in the logical channel bucket j to zero). In certain embodiments, the value of Bj can be initialized to zero for an inactive / suspended logic channel when duplication is disabled. In various embodiments, the UE 205 does not maintain the symbol bucket status of an inactive logical channel when duplication is disabled; for example, the UE 205 stops increasing the bucket status of symbols Bj.
[0100] In certain modalities, the UE 205 cancels, if any, Scheduling Requests activated and / or temporary storage status reports caused by the arrival of inactive / suspended logical channel data when duplication is deactivated. Note that the Escalation Request (s) and / or temporary storage status report (s) are activated by data arrival for the logical channel now inactive.
[0101] In some modalities, the MAC 605 entity discards packets that are received for an RLC entity that is suspended or inactive when duplication is disabled. Note that RLC PDUs of an inactive RLC entity / logical channel may still be subject to retransmission
HARQ and for this reason arrive after duplication Tue been disabled. [0102] A figure 7 represents a method 700 for duplicate PDUs from PDCP for a carrier of radio , in
according to disclosure modalities. In some embodiments, method 700 is performed by a remote unit, such as remote unit 105, UE 205 and / or user equipment apparatus 300, described
Petition 870190107476, dated 10/23/2019, p. 63/89
47/57 previously. In some embodiments, method 700 is executed by a processor executing program code; for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA or similar.
[0103] Method 700 begins and establishes a radio carrier in 705 to communicate with a mobile communication network. Here, the radio carrier includes a PDCP entity, first and second RLC entities associated with said PDCP entity, a first logical channel associated with the first RLC entity, and a second logical channel associated with the second RLC entity.
[0104] Method 700 includes receiving a control signal from the mobile communication network at 710. Here, the control signal activates PDCP duplication on the remote unit. In several embodiments, the control signal can be a PDCP control signal, a MAC control signal or an RRC signal. In certain embodiments, the first control signal initializes a symbol bucket status to a previously inactive logical channel, a number of symbols in the symbol bucket being incremented periodically, where the previously inactive logical channel is one of the first logical channel and the second logical channel.
[0105] Method 700 includes duplicating 715 PDUs of PDCP data in the PDCP entity. In some embodiments, duplicating 715 PDUs of PDCP data may include indicating an amount of PDCP data PDUs in the PDCP entity for a MAC entity associated with the first RLC entity and for a MAC entity associated with the second RLC entity to report the temporary storage status of
Petition 870190107476, dated 10/23/2019, p. 64/89
48/57 logical channels associated with the first RLC entity and second RLC entity. In one embodiment, the MAC entity associated with the first RLC entity is different from the MAC entity associated with the second RLC entity, for example, where the remote unit is configured with a split carrier. In another embodiment, the MAC entity associated with the first RLC entity is the same MAC entity associated with the second RLC entity, for example, where the remote unit is configured for carrier aggregation.
[0106] Method 700 includes submitting 720 duplicate PDCP data PDUs to the first RLC entity and the second RLC entity for transmission. Transmission can take place according to UL concessions for the first RLC entity and the second RLC entity.
[0107] Method 700 includes indicating at 725 for one of the first RLC entity and the second RLC protocol entity to discard one or more PDUs of duplicate PDCP data in response to receiving confirmation of successful transmission of one or more PDUs corresponding PDCP data by the other RLC entity. In some embodiments, the other RLC protocol entity indicates the successful delivery of one or more PDUs of corresponding PDCP data to the PDCP protocol entity based on an RLC status report received from the mobile communication network and the PDCP protocol sends a discard indication, in response to receiving said successful delivery indication, to one of the first RLC protocol entity and the second RLC protocol entity to discard one or more PDCP data PDUs
Petition 870190107476, dated 10/23/2019, p. 65/89
Duplicate 49/57. The method ends at 700.
[0108] This document reveals a first device for duplicating PDCP PDUs to a radio carrier. The first device includes a processor and a transceiver that communicates with a mobile communication network. The processor establishes a radio bearer to communicate with a mobile communication network, the radio bearer comprising a PDCP protocol entity, a first RLC protocol entity and a second RLC protocol entity being associated with said PDCP protocol entity , a first logical channel being associated with said first RLC protocol entity, and a second logical channel being associated with said second RLC protocol entity. The processor receives a first control signal from the mobile communication network, duplicates PDCP data protocol units (PDUs) in the PDCP protocol entity, and submits the duplicated PDCP data PDUs to the first RLC protocol entity and the second RLC protocol entity for transmission in response to the first control signal. In addition, the processor indicates to one of the first RLC protocol entity and the second RLC protocol entity to discard one or more duplicate PDCP data PDUs in response to receiving a successful delivery confirmation of one or more data PDUs corresponding PDCP numbers by the other RLC protocol entity.
[0109] In certain embodiments of the first device, the other RLC protocol entity indicates successful delivery of one or more PDUs of corresponding PDCP data to the PDCP protocol entity based on
Petition 870190107476, dated 10/23/2019, p. 66/89
50/57 in an RLC status report received from the mobile communication network and the PDCP protocol entity sends a discard indication, in response to receiving said successful delivery indication, to one of the first RLC protocol entity and the second RLC protocol entity to drop one or more PDUs of duplicate PDCP data. In such embodiments, the processor may also discard one or more PDCPs of PDCP data in one of the first RLC protocol entity and the second RLC protocol entity in response to receiving the disposal indication from the PDCP protocol entity. In other embodiments of the first device, the processor discards one or more PDUs of PDCP data in one of the first RLC protocol entity and the second RLC protocol entity based on a PDCP status report received from the mobile communication network.
[0110] In certain embodiments of the first apparatus, the processor additionally indicates a quantity of PDCP data PDUs in the PDCP protocol entity for a MAC entity associated with the first RLC protocol entity and for a MAC entity associated with the second data entity RLC protocol to report the temporary storage status of the logical channels associated with the first RLC protocol entity and the second RLC protocol entity, in response to the first control signal.
[0111] In some of these modalities, each of the RLC protocol entities belongs to a different group of cells in the mobile communication network, where the MAC entity associated with the first RLC protocol entity is
Petition 870190107476, dated 10/23/2019, p. 67/89
51/57 a first MAC entity and the MAC entity associated with the second RLC protocol entity is a second MAC entity different from the first, where the processor indicates the same amount of PDCP data PDUs in the PDCP protocol entity for the first MAC entity and for the second MAC entity to report the temporary storage status of the first logical channel and the second logical channel. Here, a split carrier can be established on the apparatus and where the first control signal comprises an indication to duplicate PDUs of PDCP data on the split carrier. In addition, the processor can establish a rise link data split threshold to zero in response to receiving the first control signal, the first control signal enabling packet duplication, and establish the rise link data split threshold to infinity in response to receiving a second control signal, the second control signal disabling packet duplication.
[0112] In other such modalities, the first RLC protocol entity and the second RLC protocol entity belong to the same Group of Cells, in which the MAC entity associated with the first RLC protocol entity and the MAC entity associated with the second RLC protocol entities are the same MAC entity, where the processor indicates the same amount of PDCP data PDUs in the PDCP protocol entity for the same MAC entity to report the temporary storage status of the first logical channel and the second channel logical. Here, the processor can receive a second control signal and disable packet duplication, where the processor indicates
Petition 870190107476, dated 10/23/2019, p. 68/89
52/57 a number of PDCP data PDUs available for transmission in the PDCP protocol entity to the MAC entity associated with the second RLC protocol entity to report temporary storage status of the second logical channel to zero in response to the second control. In addition, the processor can receive a third control signal before the second control signal, the third control signal indicating to use the first RLC protocol entity to transmit PDUs of PDCP data when disabling packet duplication.
[0113] In certain embodiments of the first device, the first control signal instructs the device to begin duplicating PDUs of PDCP data. Here, the processor can receive a second control signal that instructs the device to stop duplicating PDUs of PDCP data. In some of these modalities, the processor cancels an escalation request associated with the second logical channel in response to the second control signal, the escalation request being activated by data arrival to the second logical channel. In other embodiments, the processor may cancel a temporary storage status report associated with the second logical channel in response to the second control signal, the temporary storage status report being activated by data arrival for the second logical channel.
[0114] In certain modalities of the first device, the first control signal initializes a symbol bucket status to a previously inactive logical channel, a number of symbols in the symbol bucket being incremented periodically, in which the logical channel is inactive
Petition 870190107476, dated 10/23/2019, p. 69/89
53/57 is previously one of the first logical channel and the second logical channel. In such embodiments, the processor additionally receives a second control signal, the second control signal disabling packet duplication, in which the processor does not maintain a bucket of symbols associated with the second logic channel in response to the second control signal.
[0115] In certain modalities of the first device, the first control signal is one of: a PDCP control signal, a MAC control signal and an RRC signal.
[0116] This document discloses a first method for duplicating PDCP PDUs to a radio carrier. The first method includes establishing, on a remote unit, a radio bearer to communicate with a mobile communication network, the radio bearer comprising a PDCP protocol entity, a first RLC protocol entity and a second RLC protocol entity being associated with said PDCP protocol entity, a first logical channel being associated with said first RLC protocol entity, and a second logical channel being associated with said second RLC protocol entity. The first method includes receiving, on the remote unit, a first control signal from the mobile communication network, duplicating PDCP data PDUs on the remote unit on the PDCP protocol entity, and submitting the duplicated PDCP PDUs to the first protocol entity RLC and the second RLC protocol entity for transmission, in response to the first control signal. The first method also includes indicating to one of the first RLC protocol entity and the second protocol entity
Petition 870190107476, dated 10/23/2019, p. 70/89
54/57
RLC to discard one or more duplicate PDCP data PDUs in response to receiving confirmation of successful transmission of one or more corresponding PDCP data PDUs by the other RLC protocol entity.
[0117] In certain modalities of the first method, the
another entity RLC protocol indicates the delivery good- successful of an or more Data PDUs in PDCP corresponding to the entity in protocol PDCP with base in a report of status RLC Received gives network in
mobile communication. Here, the PDCP protocol entity indicates to one of the first RLC protocol entity and the second RLC protocol entity to discard one or more PDUs of duplicate PDCP data, in response to receiving said indication of successful delivery. . In such embodiments, the first method includes disposing one or more PDUs of PDCP data in one of the first RLC protocol entity and the second RLC protocol entity in response to receiving the disposal indication from the PDCP protocol entity. In other embodiments, the first method includes dropping one or more PDUs of PDCP data into one of the first RLC protocol entity and the second RLC protocol entity based on a PDCP status report received from the mobile communication network.
[0118] In certain embodiments, the first method includes indicating a quantity of PDCP data PDUs in the PDCP protocol entity for a MAC entity associated with the first RLC protocol entity and for a MAC entity associated with the second RLC protocol entity to report the temporary storage status of the logical channels associated with the first
Petition 870190107476, dated 10/23/2019, p. 71/89
55/57 RLC protocol and with the second RLC protocol entity, in response to the first control signal.
[0119] In certain embodiments of the first method, each of the RLC protocol entities belongs to a different group of cells in the mobile communication network, where the MAC entity associated with the first RLC protocol entity is a first MAC entity and the MAC entity associated with the second RLC protocol entity is a second MAC entity different from the first, where the remote unit indicates the same amount of PDCP data PDUs in the PDCP protocol entity for the first MAC entity and for the second MAC entity to report the temporary storage status of the first logical channel and the second logical channel. In such embodiments, a split carrier is established on the remote unit, where the first control signal comprises an indication to duplicate PDUs of PDCP data on the split carrier. In some embodiments, the first method includes establishing a threshold for dividing uplink data to zero in response to receiving the first control signal and establishing the threshold for dividing upstream data to infinity in response to receiving a second control signal, where the first control signal enables packet duplication and the second control signal disables packet duplication.
[0120] In certain embodiments of the first method, the first RLC protocol entity and the second RLC protocol entity belong to the same group of cells, where the MAC entity associated with the first RLC protocol entity and the MAC entity associated with the second
Petition 870190107476, dated 10/23/2019, p. 72/89
56/57 RLC protocol entities are the same MAC entity. In such embodiments, the first method includes indicating the same amount of PDCP data PDUs in the PDCP protocol entity for the same MAC entity to report the temporary storage status of the first logical channel and the second logical channel. In some embodiments, the first method includes receiving a second control signal and disabling packet duplication, in which the remote unit indicates a number of PDCP data PDUs available for transmission in the PDCP protocol entity to the MAC entity associated with the second RLC protocol entity to report temporary storage status of the second logical channel to zero in response to the second control signal. In some embodiments, the first method includes receiving a third control signal before the second control signal, the third control signal indicating to use the first RLC protocol entity to transmit PDUs of PDCP data when disabling packet duplication.
[0121] In certain embodiments of the first method, the first control signal instructs the remote unit to begin duplicating PDUs of PDCP data, the first method additionally including receiving a second control signal which instructs the remote unit to stop duplicating PDUs of PDCP data. In some embodiments, the first method includes canceling an escalation request associated with the second logical channel in response to the second control signal, the escalation request being activated by data arrival to the second logical channel. In some modalities, the first
Petition 870190107476, dated 10/23/2019, p. 73/89
57/57 method includes canceling a staging status report associated with the second logical channel in response to the second control signal, the staging status report being activated by data arrival for the second logical channel.
[0122] In certain embodiments, the first method includes initializing a symbol bucket status to a previously inactive logical channel, a number of symbols in the symbol bucket being incremented periodically, where the previously inactive logical channel is one of the first channel logical and the second logical channel. In such embodiments, the first method may include receiving a second control signal, the second control signal disabling packet duplication, in which the remote unit does not maintain a bucket of symbols associated with the second logical channel in response to the second control signal . In various modalities of the first method, the first control signal is one of: a PDCP control signal, a MAC control signal and an RRC signal.
[0123] Modalities can be practiced in other specific ways. The described modalities should be considered in all aspects only as illustrative and not restrictive. The scope of the invention, therefore, is indicated by the appended claims instead of the previous description. All changes that fall within the meaning and equivalence range of the claims must be within your scope.

权利要求:
Claims (7)
[1]
1. Device, characterized by the fact that it comprises:
a transceiver that communicates with a mobile communication network; and a processor that:
establishes a radio bearer to communicate with a mobile communication network, the radio bearer comprising a Packet Data Convergence Protocol (PDCP) protocol entity, a first Radio Link Control protocol (RLC) entity and a second RLC protocol entity being associated with said PDCP protocol entity, a first logical channel being associated with said first
entity of protocol RLC, and one second logical channel being associated with the said second entity in protocol RLC;receive a first signal in control gives network Communication mobile; duplicates units of Dice in protocol ( PDUs) of
PDCP data in the PDCP protocol entity and submits the duplicated PDCP data PDUs to the first RLC protocol entity and the second RLC protocol entity for transmission in response to the first control signal; and indicates for one of the first RLC protocol entity and the second RLC protocol entity to discard one or more duplicate PDCP data PDUs in response to receiving a successful delivery confirmation of one or more corresponding PDCP data PDUs by the other RLC protocol entity.
Petition 870190107476, dated 10/23/2019, p. 75/89
[2]
2/7
2. Apparatus according to claim 1, characterized by the fact that the other RLC protocol entity indicates the successful delivery of one or more PDUs of corresponding PDCP data to the PDCP protocol entity based on a report of RLC status received from the mobile communication network and the PDCP protocol entity indicates, in response to receiving said indication of successful delivery, to one of the first RLC protocol entity and the second RLC protocol entity to discard to one or more duplicate PDCP data PDUs.
[3]
3. Apparatus according to claim 2, characterized by the fact that the processor additionally discards one or more PDUs of PDCP data in one of the first RLC protocol entity and the second RLC protocol entity in response to receiving the indication for disposal of the PDCP protocol entity.
[4]
4. Apparatus according to claim 1, characterized by the fact that the processor discards one or more PDUs of PDCP data in one of the first RLC protocol entity and the second RLC protocol entity based on a report of PDCP status received from the mobile communication network.
[5]
5. Apparatus according to claim 1, characterized by the fact that the processor additionally indicates a quantity of PDCP data PDUs in the PDCP protocol entity for a media access control entity (MAC) associated with the first entity protocol entity and for a MAC entity associated with the second RLC entity to report a status
Petition 870190107476, dated 10/23/2019, p. 76/89
3/7 temporary storage of the logical channels associated with the first RLC protocol entity and the second RLC protocol entity, in response to the first control signal.
[6]
6. Apparatus, according to claim 5, characterized by the fact that each of the RLC protocol entities belongs to a different group of cells in the mobile communication network, in which the MAC entity associated with the first RLC protocol entity is a first MAC entity and the MAC entity associated with the second RLC protocol entity is a second MAC entity different from the first, where the processor indicates the same amount of PDCP data PDUs in the PDCP protocol entity for the first MAC entity and to the second MAC entity to report the temporary storage status of the first logical channel and the second logical channel.
7. Appliance, in wake up with the claim 6, featured fur fact that an split carrier is established on the device is at what the first sign in
The control comprises an indication to duplicate PDUs of PDCP data on the split carrier.
8. Apparatus according to claim 6, characterized by the fact that the processor sets a threshold for dividing uplink data to zero in response to receiving the first control signal, the first control signal activating packet duplication , and establishes the threshold for dividing uplink data to infinity in response to receiving a second control signal, the second control signal deactivating
Petition 870190107476, dated 10/23/2019, p. 77/89
4 / Ί duplication of packages.
9. Apparatus according to claim 5, characterized by the fact that the first RLC protocol entity and the second RLC protocol entity belong to the same Group of Cells, in which the MAC entity associated with the first RLC protocol entity and the MAC entity associated with the second RLC protocol entity are the same MAC entity, where the processor indicates the same amount of PDCP data PDUs in the PDCP protocol entity for the same MAC entity to report the temporary storage status of the first logical channel and the second logical channel.
10. Apparatus according to claim 9, characterized by the fact that the processor receives a second control signal and disables packet duplication, in which the processor indicates a number of PDCP data PDUs available for transmission at the PDCP protocol entity for the MAC entity associated with the second RLC protocol entity to report temporary storage status of the second logical channel to zero in response to the second control signal.
11. Apparatus according to claim 10, characterized by the fact that the processor receives a third control signal before the second control signal, the third control signal indicating to use the first RLC protocol entity for transmission of data PDUs PDCP when disabling packet duplication.
12. Apparatus according to claim 1, characterized by the fact that the first control signal instructs the apparatus to start duplicating data PDUs from
Petition 870190107476, dated 10/23/2019, p. 78/89
5/7
PDCP, the processor additionally receiving a second control signal that instructs the apparatus to stop duplicating PDUs of PDCP data.
13. Apparatus according to claim 12, characterized by the fact that the processor cancels a scheduling request associated with the second logic channel in response to the second control signal, the scheduling request being activated by data arrival for the second logical channel.
14. Apparatus according to claim 12, characterized by the fact that the processor cancels a temporary storage status report associated with the second logical channel in response to the second control signal, the temporary storage status report being activated by arrival of data for the second logical channel.
15. Apparatus according to claim 1, characterized by the fact that the first control signal initializes a symbol bucket status to a previously inactive logical channel, a number of symbols in the symbol bucket being incremented periodically, in which the previously inactive logical channel is one of the first logical channel and the second logical channel.
16. Apparatus according to claim 15, characterized by the fact that the processor additionally receives a second control signal, the second control signal disabling packet duplication, in which the processor does not maintain a bucket of symbols associated with the second logical channel in response to the second control signal.
Petition 870190107476, dated 10/23/2019, p. 79/89
6 / Ί
17. Apparatus according to claim 1, characterized by the fact that the first control signal is one of: a PDCP control signal, a MAC control signal and an RRC signal.
18. Method, characterized by the fact that it comprises:
establish, on a remote unit, a radio bearer to communicate with a mobile communication network, the radio bearer comprising a Packet Data Convergence Protocol (PDCP) protocol entity, a first Data Control protocol entity Radio link (RLC) and a second RLC protocol entity being associated with said PDCP protocol entity, a first logical channel being associated with said first RLC protocol entity, and a second logical channel being associated with said second entity of RLC protocol;
receiving, at the remote unit, a first control signal from the mobile communication network;
duplicate, on the remote unit, Protocol Data Units (PDUs) of PDCP data in the PDCP protocol entity and submit the duplicated PDCP data PDUs to the first RLC protocol entity and the second RLC protocol entity for transmission in response to first control signal; and indicating to one of the first RLC protocol entity and the second RLC protocol entity to discard one or more duplicate PDCP data PDUs in response to receiving confirmation of successful transmission of one or more corresponding PDCP data PDUs by another
Petition 870190107476, dated 10/23/2019, p. 80/89
[7]
7/7 RLC protocol entity.
19. Method, according to claim 18, characterized by the fact that it additionally comprises:
indicate, in response to the first control signal, a number of PDCP data PDUs in the PDCP protocol entity for a media access control (MAC) entity associated with the first RLC protocol entity and for a MAC entity associated with the second RLC protocol entity to report a temporary storage status of the logical channels associated with the first RLC protocol entity and the second RLC protocol entity.
20. Method according to claim 18, characterized in that the first control signal instructs the remote unit to begin duplicating PDUs of PDCP data, the method further comprising:
receive a second control signal that instructs the remote to stop duplicating PDUs of PDCP data.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019022214A2|2020-05-12|DUPLICATION OF PDCP PDUS TO A RADIO CARRIER

---

US10659992B2|2020-05-19|Switching between packet duplication operating modes

---

US11212701B2|2021-12-28|Systems, methods, and devices for ultra-reliable low latency communication quality-of-service guarantee

---

US11172395B2|2021-11-09|Determining data available for transmission

---

EP2636272B1|2018-08-29|Method and apparatus for reconfiguring connection to base station at relay node in a wireless communication system

---

BR112019023263A2|2020-05-26|TRANSMIT SR BEFORE COMPLETING RACH

---

TWI565282B|2017-01-01|Method of handling communication operation in tdd system and related apparatus

---

TWI706652B|2020-10-01|Device and method of handling buffer status reporting for packet duplication

---

US20200235898A1|2020-07-23|Autonomous bandwidth part switching

---

WO2017016351A1|2017-02-02|Uplink data transmission method and device

---

EP3928453A2|2021-12-29|Autonomously triggering retransmission of data

---

WO2017008747A1|2017-01-19|Method and device for transmitting and receiving downlink data feedback information

---

US20200187235A1|2020-06-11|Method, apparatus, computer program product and computer program

---

TWI535319B|2016-05-21|Method of handling resource allocation in tdd system and related communication device

---

US20200259627A1|2020-08-13|Efficient bwp operation for sidelink operation

---

EP3874636A1|2021-09-08|Apparatus, method and computer program

---

WO2017049528A1|2017-03-30|Configuration method for transmission time interval, and data transmission method, apparatus and system

---

US20210168840A1|2021-06-03|Buffer status report for packet duplication

---

US20220007390A1|2022-01-06|Determining uplink grants for multiple modes

---

WO2021152514A1|2021-08-05|Preventing transmission when switching an active uplink bandwidth part

---

CN112740758A|2021-04-30|Handover request with network information

同族专利:

---

公开号 | 公开日

---

US10574564B2|2020-02-25|

---

EP3616440A1|2020-03-04|

---

WO2018200565A1|2018-11-01|

---

CN110945901B|2022-03-01|

---

US20200228438A1|2020-07-16|

---

US20180309660A1|2018-10-25|

---

CN110945901A|2020-03-31|

---

KR20190139886A|2019-12-18|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US6751746B1|2000-07-31|2004-06-15|Cisco Technology, Inc.|Method and apparatus for uninterrupted packet transfer using replication over disjoint paths|

---

US20060013210A1|2004-06-18|2006-01-19|Bordogna Mark A|Method and apparatus for per-service fault protection and restoration in a packet network|

---

KR101669966B1|2009-05-11|2016-10-27|엘지전자 주식회사|Method for transmitting and receiving duplicated data in a multi-carrier supported wireless communication system and appratus for the same|

---

US8989004B2|2010-11-08|2015-03-24|Qualcomm Incorporated|System and method for multi-point HSDPA communication utilizing a multi-link PDCP sublayer|

---

EP2568673A1|2011-08-30|2013-03-13|ABB Technology AG|Parallel Redundancy Protocol, PRP, packet duplication over VLANs based on Spanning Tree instances.|

---

US8958422B2|2012-03-17|2015-02-17|Blackberry Limited|Handling packet data convergence protocol data units|

---

US8988994B2|2013-05-16|2015-03-24|Freescale Semiconductor, Inc.|System and method for creating logical radio link control and medium access control protocol data units in mobile communication system|

---

EP2854444A1|2013-09-27|2015-04-01|Panasonic Intellectual Property Corporation of America|Efficient uplink scheduling mechanism for dual connectivity|

---

GB2520923B|2013-11-01|2017-07-26|Samsung Electronics Co Ltd|Bearer reconfiguration|

---

US10716094B2|2017-03-23|2020-07-14|Ofinno, Llc|Packet duplication in a wireless device and wireless network|

---

US10536878B2|2017-03-24|2020-01-14|Mediatek Inc.|User equipment and methods for PDCP duplication in 5G RAN|

---

US10405231B2|2017-04-24|2019-09-03|Motorola Mobility Llc|Switching between packet duplication operating modes|

---

US11129234B2|2018-02-13|2021-09-21|FG Innovation Company Limited|Methods for packet data convergence protocol duplication operations and devices using the same|US10750410B2|2016-09-30|2020-08-18|Huawei Technologies Co., Ltd.|Ultra reliable low latency connection support in radio access networks|

---

EP3554166A4|2017-01-13|2020-08-12|Samsung Electronics Co., Ltd.|Method and device for transmitting data packet in wireless communication system|

---

WO2018164616A1|2017-03-09|2018-09-13|Telefonaktiebolaget Lm Ericsson |Methods and apparatus for packet communication over a local network using a local packet replication procedure|

---

US10237784B2|2017-03-24|2019-03-19|Motorola Mobility Llc|Split bearer packet data converge protocol protocol data unit routing|

---

CN108633093B|2017-03-24|2019-08-02|电信科学技术研究院|A kind of buffer region state reporting method, UE, the processing method of Buffer Status Report and network side equipment|

---

KR102318015B1|2017-04-28|2021-10-27|삼성전자 주식회사|Method and appatarus for indicating data length according to data type in wireless communication system|

---

EP3399724A1|2017-05-05|2018-11-07|ASUSTek Computer Inc.|Method and apparatus of transmitting data duplication in a wireless communication system|

---

US10805836B2|2017-05-05|2020-10-13|Qualcomm Incorporated|Packet duplication at a packet data convergence protocolentity|

---

EP3941153A1|2017-05-05|2022-01-19|Samsung Electronics Co., Ltd.|Data transmission method and network equipment supporting pdcp duplication function|

---

WO2018221926A1|2017-06-02|2018-12-06|Lg Electronics Inc.|Apparatus and method for performing packet duplication|

---

CN109246710A|2017-06-09|2019-01-18|夏普株式会社|Base station, user equipment and correlation technique|

---

WO2018230849A1|2017-06-14|2018-12-20|Lg Electronics Inc.|Method for handling deactivation for a cell in which packet duplication is performed in wireless communication system and a device therefor|

---

US10659381B2|2017-06-16|2020-05-19|Mediatek Singapore Pte. Ltd.|Method and apparatus for handling data duplication in mobile communications|

---

US20180367288A1|2017-06-16|2018-12-20|Huawei Technologies Co., Ltd.|Dynamic activation and deactivation of packet duplication|

---

US10728878B2|2017-06-22|2020-07-28|FB Innovation Company Limited|Systems, devices, and methods for packet data convergence protocol packet data unit duplication|

---

WO2019009772A1|2017-07-05|2019-01-10|Telefonaktiebolaget Lm Ericsson |Enabling efficient handling of redundant packet copies in a wireless communication system|

---

EP3661090A4|2017-07-28|2021-03-10|Fujitsu Limited|Command instruction method and device, and information interaction method and device|

---

JP2020532888A|2017-07-28|2020-11-12|オッポ広東移動通信有限公司Ｇｕａｎｇｄｏｎｇ Ｏｐｐｏ Ｍｏｂｉｌｅ Ｔｅｌｅｃｏｍｍｕｎｉｃａｔｉｏｎｓ Ｃｏｒｐ．， Ｌｔｄ．|Data transmission method, terminal equipment and network equipment|

---

SG11201911628TA|2017-07-28|2020-01-30|Guangdong Oppo Mobile Telecommunications Corp Ltd|Data transmission method and related product|

---

EP3635900B1|2017-08-16|2022-01-12|Samsung Electronics Co., Ltd.|Method and apparatus for transmitting and receiving duplicate packets in next-generation mobile communication system|

---

BR112020003446A2|2017-08-21|2021-02-02|Beijing Xiaomi Mobile Software Co., Ltd.|data transmission method and device|

---

EP3738249A4|2018-01-10|2021-09-08|FG Innovation Company Limited|Methods and devices for packet data convergence protocoldata transmission in wireless communication systems|

---

US10772008B2|2018-01-11|2020-09-08|Comcast Cable Communications, Llc|Cell configuration for packet duplication|

---

US10869223B2|2018-02-13|2020-12-15|Samsung Electronics Co., Ltd.|Method and apparatus for efficient operation upon packet duplication activation and deactivation in next generation wireless communication system|

---

TWI713399B|2018-08-03|2020-12-11|華碩電腦股份有限公司|Method and apparatus for handling sidelink reception in a wireless communication system|

---

WO2020118991A1|2018-12-11|2020-06-18|Oppo广东移动通信有限公司|Wireless communication method, terminal device, and network device|

---

WO2020118519A1|2018-12-11|2020-06-18|Oppo广东移动通信有限公司|Wireless communication method, terminal device and network device|

---

EP3909387A1|2019-01-08|2021-11-17|NEC Corporation|Core network node and method for handling redundant urllc connections|

---

CN112655259A|2019-01-16|2021-04-13|Oppo广东移动通信有限公司|Data copy transmission configuration method, device, chip and computer program|

---

CN112715044A|2019-01-18|2021-04-27|Oppo广东移动通信有限公司|Data copying method, terminal equipment and storage medium|

---

CN112586016A|2019-01-28|2021-03-30|Oppo广东移动通信有限公司|Data copying and transmission control method, terminal equipment and network equipment|

---

CN111866969B|2019-04-30|2021-10-26|华为技术有限公司|Data processing method, communication device and system|

---

CN112243279A|2019-07-18|2021-01-19|华为技术有限公司|Method, related device and system for realizing service continuity|

---

WO2021016790A1|2019-07-29|2021-02-04|Oppo广东移动通信有限公司|Method for radio communication, terminal device, and network device|

---

US20210105844A1|2019-10-03|2021-04-08|Qualcomm Incorporated|Mac-ce design and power headroom considerations for pdcp duplication enhancements|

---

WO2021097689A1|2019-11-19|2021-05-27|华为技术有限公司|Communication method, apparatus and device|

---

CN113038632A|2019-12-24|2021-06-25|夏普株式会社|Control method of PDCP entity and PDCP entity|

---

CN113498152A|2020-04-01|2021-10-12|夏普株式会社|Method performed by user equipment and user equipment|

---

WO2022016364A1|2020-07-21|2022-01-27|Mediatek Singapore Pte. Ltd.|Methods and apparatus of multicast and broadcast service reception|

法律状态:
2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762489332P| true| 2017-04-24|2017-04-24|

---

US62/489,332|2017-04-24|

---

US15/961,510|US10574564B2|2017-04-24|2018-04-24|Duplicating PDCP PDUS for a radio bearer|

---

US15/961,510|2018-04-24|

---

PCT/US2018/029194|WO2018200565A1|2017-04-24|2018-04-24|Duplicating pdcp pdus for a radio bearer|

---